Dear Infinispanners,

The C++ and C# 8.3.0.Final releases are out!

Main features contained in this release are:

Source code, binaries and docs are available as usual at the links below.

Thank you for reading, The Infinispan Team

Release notes for the 8.3.0 serie [2] https://github.com/infinispan/cpp-client/tree/8.3.0.Final[C code for 8.3.0.Final] [2#] C# code for 8.3.0.Final

Dear Infinispanners,

The C++ and C# 8.3.0.Alpha1 releases are available!

Both the clients come with these new features:

For the .NET Core lovers, there’s a work in progress to implement the dotnet core build for the C# client [3]. Features list, code and bits are available as usual: [4] [5] [6].

Cheers, The Infinispan Team

Clustered Counters

Hot Rod Admin Tasks

How to build à la .NET Core manière

Release notes [5] https://github.com/infinispan/cpp-client/tree/8.3.0.Alpha1[C code for 8.3.0.Alpha1]

C# code for 8.3.0.Alpha1

We’re pleased to announce the availability of the 8.2.0.Final release of the C++ and C# Hotrod clients. Here is what happened in the 8.2.0 episode:

C++

C#

You can find more info and even the binaries at the usual places

In the backstage people are already working on the 8.3.0 episode, you can partecipate expressing your opinion or adding your ideas here [5][6].

Thank you for reading.

The Infinispan Team

[5] C++ Features List for 8.3.0 [6] C# Features List for 8.3.0

Dears,

we’re pleased to announce that 8.1.0.Final release for C++/C# clients is out!

Check the Release Notes and try it yourself without fear, it’s tagged as stable!

As in the best TV series: Final doesn’t mean the last! Stay tuned for the next 8.2.0 "More Fun Is Coming" season :)

Enjoy and thanks for reading!

The Infinispan Team

Dear Readers,

as mentioned in our previous post about the new C++/C# release 8.1.0.Beta1, clients are now equipped with near cache support.

The near cache is an additional cache level that keeps the most recently used cache entries in an "in memory" data structure. Near cached objects are synchronized with the remote server value in the background and can be get as fast as a map[] operation.

So, your client tends to periodically focus the operations on a subset of your entries? This feature could be of help: it’s easy to use, just enable it and you’ll have near cache seamless under the wood.

A C++ example of a cache with near cache configuration

The last line does the magic, the INVALIDATED mode is the active mode for the near cache (default mode is DISABLED which means no near cache, see Java docs), maxEntries is the maximum number of entries that can be stored nearly. If the near cache is full the oldest entry will be evicted. Set maxEntries=0 for unbounded cache (do you have enough memory?) Now a full example of application that just does some gets and puts and counts how many of them are served remote and how many are served nearly. As you can see the cache object is an instance of the "well known" RemoteCache class

Entries values in the near cache are kept aligned with the remote cache state via the events subsystem: if something changes in the server, an update event (modified, expired, removed) is sent to the client that updates the cache accordingly.

By the way: do you know that C++/C# clients can subscribe listener to events? In the next "native" post we will see how.

Cheers! and thank you for reading.